Unified product catalog data retrieval and modification

ABSTRACT

Embodiments for providing a unified catalog include systems and methods that import catalog data from one or more underlying catalog systems. The systems identify items from the catalog data and modify at least one of item descriptions, item names, product categories, and item identifiers associated with the identified items. The systems further provide a unified user interface to a user for browsing the items, receive a request for at least one product selected by the user from the items, and send an order for the at least one selected product to the one or more catalog systems.

BACKGROUND

Sophisticated companies often have internal technical support systemsfor supporting the needs of their employees. When these sophisticatedcompanies merge or undergo restructuring, the systems tend to exist asindependent and separate systems. Employees of the merged companies maynot be aware of all of the resources available to them or know how toaccess and use the independent and separate systems. Moreover, theservices and goods offered by these disparate systems may overlapcreating a waste of resources.

BRIEF SUMMARY

The following presents a simplified summary of one or more embodimentsof the invention in order to provide a basic understanding of suchembodiments. This summary is not an extensive overview of allcontemplated embodiments, and is intended to neither identify key orcritical elements of all embodiments, nor delineate the scope of any orall embodiments. Its sole purpose is to present some concepts of one ormore embodiments in a simplified form as a prelude to the more detaileddescription that is presented later.

The embodiments are directed to systems for providing a unified catalog,whereby the system collects, manages, and edits catalog data fromdisparate catalog systems. The system includes a computer apparatusincluding a processor and a memory and a software module stored in thememory, comprising executable instructions that when executed by theprocessor cause the processor to import catalog data from one or moreunderlying catalog systems. In some embodiments, the executableinstructions further cause the processor to identify items from thecatalog data. In some embodiments, the executable instructions furthercause the processor to modify at least one of item descriptions, itemnames, product categories, and item identifiers associated with theidentified items. In some embodiments, the executable instructionsfurther cause the processor to provide a unified user interface to auser for browsing the items. In some embodiments, the executableinstructions further cause the processor to receive a request for atleast one product selected by the user from the items. In someembodiments, the executable instructions further cause the processor tosend an order for the at least one selected product to the one or morecatalog systems.

In further embodiments, the executable instructions further cause theprocessor to identify a first product category comprising at least onecategory item and transfer the at least one category item to a secondproduct category. In some embodiments, the at least one category itemappears in the first product category and the second product category.In other embodiments, the executable instructions further cause theprocessor to collapse the first product category. In still otherembodiments, the executable instructions further cause the processor torename the first product category. In additional embodiments, theexecutable instructions further cause the processor to identify relateditems associated with a product category from the catalog data; create aproduct package comprising the related items; and present the productpackage to the user via the user interface.

In still further embodiments, the executable instructions further causethe processor to set at least one of a service level agreement (SLA)time period, a user group, and approval requirements for the items. Inother embodiments, the executable instructions further cause theprocessor to determine a unique identifier associated with each of theitems; identify duplicates of a single item from multiple catalogsystems based on the unique identifier; identify a preferred catalogsystem; and retain the single item associated with the preferred catalogsystem and remove all other duplicates. In still other embodiments, theexecutable instructions further cause the processor to dynamically editdisplayed data in the user interface. In some embodiments, theexecutable instructions further cause the processor to identify aplurality of related items having a plurality of different names; assigna synonym to each of the related items; allow the user to conduct anitem search using one of the different names; and display all of therelated items in response to the search and based on the synonymassignment. In additional embodiments, the order is fulfilled by the oneor more catalog systems.

Also provided are embodiments directed to computer program products forproviding a unified catalog, whereby the computer program productcollects, manages, and edits catalog data from disparate catalogsystems. The computer program products include a non-transitory computerreadable storage medium having computer readable program code embodiedtherewith, the computer readable program code comprising computerreadable program code configured to import catalog data from one or moreunderlying catalog systems.

In some embodiments, the computer program products further includecomputer readable program code configured to identify items from thecatalog data. In some embodiments, the computer program products furtherinclude computer readable program code configured to modify at least oneof item descriptions, item names, product categories, and itemidentifiers associated with the identified items. In some embodiments,the computer program products further include computer readable programcode configured to provide a unified user interface to a user forbrowsing the items. In some embodiments, the computer program productsfurther include computer readable program code configured to receive arequest for at least one product selected by the user from the items. Insome embodiments, the computer program products further include computerreadable program code configured to send an order for the at least oneselected product to the one or more catalog systems.

In further embodiments, the computer program products further includecomprising computer readable program code configured to identify a firstproduct category comprising at least one category item and transfer theat least one category item to a second product category. In stillfurther embodiments, the at least one category item appears in the firstproduct category and the second product category.

In additional embodiments, the computer program products further includecomputer readable program code configured to determine a uniqueidentifier associated with each of the items; identify duplicates of asingle item from multiple catalog systems based on the uniqueidentifier; identify a preferred catalog system; and retain the singleitem associated with the preferred catalog system and remove all otherduplicates.

In other embodiments, the computer program products further includecomputer readable program code configured to identify a plurality ofrelated items having a plurality of different names; assign a synonym toeach of the related items; allow the user to conduct an item searchusing one of the different names; and display all of the related itemsin response to the search and based on the synonym assignment.

Further provided herein are computer-implemented methods for providing aunified product catalog. In some embodiments, the methods includeimporting, by a processor. catalog data from one or more underlyingcatalog systems. In some embodiments, the methods include identifying,by a processor, items from the catalog data. In some embodiments, themethods include modifying, by a processor, at least one of itemdescriptions, item names, product categories, and item identifiersassociated with the identified items. In some embodiments, the methodsinclude providing, by a processor, a unified user interface to a userfor browsing the items. In some embodiments, the methods includereceiving a request for at least one product selected by the user fromthe items. In some embodiments, the methods include sending, by aprocessor, an order for the at least one selected product to the one ormore catalog systems.

In further embodiments, the methods include identifying, by a processor.a first product category comprising at least one category item andtransferring, by a processor. the at least one category item to a secondproduct category. In additional embodiments, the methods includedetermining, by a processor, a unique identifier associated with each ofthe items; identifying, by a processor, duplicates of a single item frommultiple catalog systems based on the unique identifier; identifying apreferred catalog system; and retaining the single item associated withthe preferred catalog system and remove all other duplicates. In someembodiments, the methods include identifying a plurality of relateditems having a plurality of different names; assigning a synonym to eachof the related items; allowing the user to conduct an item search usingone of the different names; and displaying all of the related items inresponse to the search and based on the synonym assignment.

Other aspects and features, as recited by the claims, will becomeapparent to those skilled in the art upon review of the followingnon-limited detailed description of the invention in conjunction withthe accompanying figures.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

The present embodiments are further described in the detaileddescription which follows in reference to the noted plurality ofdrawings by way of non-limiting examples of the present embodiments inwhich like reference numerals represent similar parts throughout theseveral views of the drawings and wherein:

FIG. 1 provides a block diagram illustrating a system and environmentfor creating and maintaining a unified product catalog in accordancewith the embodiments presented herein;

FIG. 2 provides a block diagram illustrating the unified catalog system,the first catalog system, and the user's device of FIG. 1, in accordancewith various embodiments;

FIG. 3 is a flowchart illustrating a system and method for creating andmaintaining a unified product catalog in accordance with variousembodiments;

FIG. 4 is a flowchart illustrating a system and method for creating andmaintaining a unified product catalog in accordance with variousembodiments;

FIG. 5 is an exemplary graphical user interface (GUI) of anadministrative tool for a unified catalog system in accordance withvarious embodiments;

FIG. 6 is an exemplary graphical user interface (GUI) of anadministrative tool for a unified catalog system in accordance withvarious embodiments;

FIG. 7 is an exemplary graphical user interface (GUI) of anadministrative tool for a unified catalog system in accordance withvarious embodiments;

FIG. 8 is an exemplary graphical user interface (GUI) of anadministrative tool for a unified catalog system in accordance withvarious embodiments;

FIG. 9 is an exemplary graphical user interface (GUI) of a unifiedproduct catalog in accordance with various embodiments;

FIG. 10 is an exemplary graphical user interface (GUI) of a unifiedproduct catalog in accordance with various embodiments;

FIG. 11 is an exemplary graphical user interface (GUI) of a unifiedproduct catalog in accordance with various embodiments; and

FIG. 12 is an exemplary graphical user interface (GUI) of a unifiedproduct catalog in accordance with various embodiments.

DETAILED DESCRIPTION

The embodiments presented herein are directed to systems, methods, andcomputer program products for creating and maintaining a unified productcatalog. The embodiments take advantage of existing infrastructure toeliminate the need to reconfigure disparate systems or merge suchsystems together. The systems and methods retrieve catalog data fromindependent and separate underlying catalog systems using APIs providedby the catalog systems. The catalog data can be modified andreconfigured to remove product duplicates, suppress overlapping productcategories, and enhance order fulfillment. A unified product catalog isprovided to the user for browsing and ordering items collected from theunderlying catalog systems. The unified product catalog is configured toprovide a streamlined service to the user such that the user may beunaware of the various underlying catalog systems that supply theordered products. In this way, a simplified and cohesive catalogexperience is provided to the user.

The embodiments of the disclosure may be embodied as a system, method,or computer program product. Accordingly, aspects of the presentdisclosure may take the form of an entirely hardware embodiment, anentirely software embodiment (including firmware, resident software,micro-code, etc.) or an embodiment combining software and hardwareaspects that may all generally be referred to herein as a “circuit,”“module” or “system.” Furthermore, aspects of the present embodiments ofthe disclosure may take the form of a computer program product embodiedin one or more computer readable medium(s) having computer readableprogram code embodied thereon.

Any combination of one or more computer readable medium(s) may beutilized. The computer readable medium may be a computer readable signalmedium or a computer readable storage medium. A computer readablestorage medium may be, for example, but not limited to, an electronic,magnetic, optical, electromagnetic, infrared, or semiconductor system,apparatus, or device, or any suitable combination of the foregoing. Morespecific examples (a non-exhaustive list) of the computer readablestorage medium would include the following: an electrical connectionhaving one or more wires, a portable computer diskette, a hard disk, arandom access memory (RAM), a read-only memory (ROM), an erasableprogrammable read-only memory (EPROM or Flash memory), an optical fiber,a portable compact disc read-only memory (CD-ROM), an optical storagedevice, a magnetic storage device, or any suitable combination of theforegoing. In the context of this document, a computer readable storagemedium may be any tangible medium that can contain, or store a programfor use by or in connection with an instruction execution system,apparatus, or device.

A computer readable signal medium may include a propagated data signalwith computer readable program code embodied therein, for example, inbaseband or as part of a carrier wave. Such a propagated signal may takeany of a variety of forms, including, but not limited to,electro-magnetic, optical, or any suitable combination thereof. Acomputer readable signal medium may be any computer readable medium thatis not a computer readable storage medium and that can communicate,propagate, or transport a program for use by or in connection with aninstruction execution system, apparatus, or device.

Program code embodied on a computer readable medium may be transmittedusing any appropriate medium, including but not limited to wireless,wireline, optical fiber cable, RF, etc., or any suitable combination ofthe foregoing. Computer program code for carrying out operations foraspects of the present embodiments of the disclosure may be written inany combination of one or more programming languages, including anobject oriented programming language such as Java, Smalltalk, C++ or thelike and conventional procedural programming languages, such as the “C”programming language or similar programming languages. The program codemay execute entirely on the user's computer, partly on the user'scomputer, as a stand-alone software package, partly on the user'scomputer and partly on a remote computer or entirely on the remotecomputer or server. In the latter scenario, the remote computer may beconnected to the user's computer through any type of network, includinga local area network (LAN) or a wide area network (WAN), or theconnection may be made to an external computer (for example, through theInternet using an Internet Service Provider).

Aspects of the present embodiments of the disclosure are described belowwith reference to flowchart illustrations and/or block diagrams ofmethods, apparatus (systems) and computer program products according toembodiments of the embodiments of the disclosure. It will be understoodthat each block of the flowchart illustrations and/or block diagrams,and combinations of blocks in the flowchart illustrations and/or blockdiagrams, can be implemented by computer program instructions. Thesecomputer program instructions may be provided to a processor of ageneral purpose computer, special purpose computer, or otherprogrammable data processing apparatus to produce a machine, such thatthe instructions, which execute via the processor of the computer orother programmable data processing apparatus, create means forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks.

These computer program instructions may also be stored in a computerreadable medium that can direct a computer, other programmable dataprocessing apparatus, or other devices to function in a particularmanner, such that the instructions stored in the computer readablemedium produce an article of manufacture including instructions whichimplement the function/act specified in the flowchart and/or blockdiagram block or blocks.

The computer program instructions may also be loaded onto a computer,other programmable data processing apparatus, or other devices to causea series of operational steps to be performed on the computer, otherprogrammable apparatus or other devices to produce a computerimplemented process such that the instructions which execute on thecomputer or other programmable apparatus provide processes forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks.

Referring now to the figures, FIG. 1 provides a block diagramillustrating a system and environment 100 for providing unified productcatalog. The system 100 includes a user 110, a device 112 of the user110, a unified catalog system 132, a first catalog system 152, a secondcatalog system 154, and a third catalog system 156, which are incommunication with each other via a network 150 (see, FIG. 2). In someembodiments, the user 110 includes at least one of an individual orentity associated with a catalog system, an employee, a support teammember, an agent of the user, and the like. The catalog systems 152,154, 156 can include underlying systems maintained by, owned, orotherwise associated with a third party, a vendor, and the like thatfeed into the unified catalog system 132.

The unified catalog system 132 is configured to crawl the catalogsystems 152, 154, 156 to retrieve and import catalog data. In someembodiments, the catalog systems 152, 154, 156 provide data retrievalprogramming (e.g., API's) or other programs to the unified catalogsystem 132 to enable the data retrieval. The programming can beformatted to certain specifications that are compatible with the unifiedcatalog system 132. The API's act like a contract between the unifiedcatalog system 132 and the underlying catalog systems 152, 154, 156 thatallows the unified catalog system 132 to search and import the catalogdata in the underlying systems. Once the catalog data has been retrievedand imported, the unified catalog system can maintain and modify theimported catalog data. Although three unified catalog systems (i.e., thefirst catalog system 152, the second catalog system 154, and the thirdcatalog systems 156) are illustrated in FIG. 1, it will be understoodthat any number of catalog systems may be used.

In the illustrated embodiment, the unified catalog system 132 provides aunified product catalog to the user's device 112. The user 110 accessesthe unified product catalog on the user's device 112 to send data to andreceive data from the unified catalog system 132 and/or the catalogsystems 152, 154, 156. Similarly, the unified catalog system 132 and thecatalog systems 152,154, 156 can also send data to and receive data fromeach other or from the user's device 112. The transferred data sharedamong the systems and devices of FIG. 1 can include catalog data, orderdata, requests, transaction data or other files, notifications,communications, and the like.

Referring now to FIG. 2, a block diagram illustrates an environment 200for creating and maintaining a unified product catalog. The environment200 includes the user's device 112, the first catalog system 152, andthe unified catalog system 132 of FIG. 1. The environment 200 furtherincludes one or more other third party systems 292 (e.g., a partner,agent, or contractor associated with the unified catalog system 132),one or more other catalog systems 294 (e.g. the second catalog system154 and third catalog system 156), and one or more external systems 296.The systems and devices communicate with one another over the network150 and perform one or more of the various steps and/or methodsaccording to embodiments of the disclosure discussed herein. The network150 may include a local area network (LAN), a wide area network (WAN),and/or a global area network (GAN). The network 150 may provide forwireline, wireless, or a combination of wireline and wirelesscommunication between devices in the network. In one embodiment, thenetwork 150 includes the Internet.

The user's device 112, the first catalog system 152, and the unifiedcatalog 132 each includes a computer system, server, multiple computersystems and/or servers or the like. The unified catalog system 132, inthe embodiments shown has a communication device 242 communicablycoupled with a processing device 244, which is also communicably coupledwith a memory device 246. The processing device 244 is configured tocontrol the communication device 242 such that the unified catalogsystem 132 communicates across the network 150 with one or more othersystems. The processing device 244 is also configured to access thememory device 246 in order to read the computer readable instructions248, which in some embodiments includes an interfacing application 250and administrator and/or editor applications 252. The memory device 246also includes a datastore 254 or database for storing pieces of datathat can be accessed by the processing device 244.

As used herein, a “processing device,” generally refers to a device orcombination of devices having circuitry used for implementing thecommunication and/or logic functions of a particular system. Forexample, a processing device may include a digital signal processordevice, a microprocessor device, and various analog-to-digitalconverters, digital-to-analog converters, and other support circuitsand/or combinations of the foregoing. Control and signal processingfunctions of the system are allocated between these processing devicesaccording to their respective capabilities. The processing device 214,244, or 264 may further include functionality to operate one or moresoftware programs based on computer-executable program code thereof,which may be stored in a memory. As the phrase is used herein, aprocessing device 214, 244, or 264 may be “configured to” perform acertain function in a variety of ways, including, for example, by havingone or more general-purpose circuits perform the function by executingparticular computer-executable program code embodied incomputer-readable medium, and/or by having one or moreapplication-specific circuits perform the function.

As used herein, a “memory device” generally refers to a device orcombination of devices that store one or more forms of computer-readablemedia and/or computer-executable program code/instructions.Computer-readable media is defined in greater detail below. For example,in one embodiment, the memory device 246 includes any computer memorythat provides an actual or virtual space to temporarily or permanentlystore data and/or commands provided to the processing device 244 when itcarries out its functions described herein.

The user's device 112 includes a communication device 212 andcommunicably coupled with a processing device 214, which is alsocommunicably coupled with a memory device 216. The processing device 214is configured to control the communication device 212 such that theuser's device 112 communicates across the network 150 with one or moreother systems. The processing device 214 is also configured to accessthe memory device 216 in order to read the computer readableinstructions 218, which in some embodiments includes a web browser (orcatalog mobile) application 220 for accessing the unified productcatalog. The memory device 216 also includes a datastore 222 or databasefor storing pieces of data that can be accessed by the processing device214.

The first catalog system 152 includes a communication device 262communicably coupled with a processing device 264, which is alsocommunicably coupled with a memory device 266. The processing device 264is configured to control the communication device 262 such that thethird party system 152 communicates across the network 150 with one ormore other systems. The processing device 264 is also configured toaccess the memory device 266 in order to read the computer readableinstructions 268, which in some embodiments include a catalogapplication 270. The memory device 266 also includes a datastore 271 ordatabase for storing pieces of data that can be accessed by theprocessing device 264.

In some embodiments, the web browser application 220 and the catalogapplication 270 interact with the interfacing application 250 andadministrator and editor applications 252 to receive or provide catalogdata; send formatting instructions; provide API's, order statuses,notifications, confirmations, and transaction data; analyze transactiondata; process orders; and the like.

The applications 220, 221, 250, 252, and 270 are for instructing theprocessing devices 214, 244 and 264 to perform various steps of themethods discussed herein, and/or other steps and/or similar steps. Invarious embodiments, one or more of the applications 220, 221, 250, 252,and 270 are included in the computer readable instructions stored in amemory device of one or more systems or devices other than the systems152 and 132 and the user's capture device 112. For example, in someembodiments, the application 220 is stored and configured for beingaccessed by a processing device of one or more third party systems 292connected to the network 150. In various embodiments, the applications220, 221, 250, 252, and 270 stored and executed by differentsystems/devices are different. In some embodiments, the applications220, 221, 250, 252, and 270 stored and executed by different systems maybe similar and may be configured to communicate with one another, and insome embodiments, the applications 220, 221, 250, 252, and 270 may beconsidered to be working together as a singular application despitebeing stored and executed on different systems.

In various embodiments, one of the systems discussed above, such as theunified catalog system 132, is more than one system and the variouscomponents of the system are not collocated, and in various embodiments,there are multiple components performing the functions indicated hereinas a single device. For example, in one embodiment, multiple processingdevices perform the functions of the processing device 244 of theunified catalog system 132 described herein. In various embodiments, theunified catalog system 132 includes one or more of the external systems296 and/or any other system or component used in conjunction with or toperform any of the method steps discussed herein. For example, theunified catalog system 132 may include a financial institution system,an information technology system, and the like.

In various embodiments, the unified catalog system 132, the firstcatalog system 152, and the user's device 112 and/or other systems mayperform all or part of a one or more method steps discussed above and/orother method steps in association with the method steps discussed above.Furthermore, some or all the systems/devices discussed here, inassociation with other systems or without association with othersystems, in association with steps being performed manually or withoutsteps being performed manually, may perform one or more of the steps ofmethod 300, the other methods discussed below, or other methods,processes or steps discussed herein or not discussed herein.

The embodiments are directed to creating, maintaining, and managing aunified catalog system. As a result of mergers, acquisitions,expansions, and changing needs, a single company may have severalindependent and disparate catalog systems for ordering products.Employees who may need items such as goods or services, may have tosearch around to identify the disparate systems, and may be required tovisit several catalog systems in order to obtain the items they need.

The unified catalog system provides an interface for communication witha user that sets forth a unified interface for providing goods andservices to the user. It unifies and collapses the underlying catalogsystems into a single central system so that a user can visit a singlesource in order to find and order items. The system pools and presentsitems from all of the underlying catalog systems, and reaches out to theunderlying systems to fulfill item requests. The user may not even beaware of the underlying systems as they browse the unified catalogsystem. In this way, a unified catalog system can be created withoutcompletely overhauling and restructuring the existing systems.

To establish a bridge to the unified catalog system, disconnectedcatalog systems can be required to submit one or more applicationprogramming interfaces (APIs) in a pre-selected format. The APIs arewritten to expose data using a standard data interchange mechanism suchas SML, representational state transfer (REST), and the like. The APIsare required to perform certain functions such as crawling of thecatalog, ordering items, changing an order, and checking order status.An administrator of the unified catalog system can integrate thedisconnected catalog system into the unified catalog system using theformatted APIs provided by the disconnected catalog system. Thepre-formatted APIs provided by the various disparate systems ensuresthat the integration is a smooth and efficient process.

FIG. 3 illustrates a flowchart providing an overview of a process 300for providing and maintaining a unified product catalog. One or moredevices, such as the one or more computing devices and/or one or moreother computing devices and/or servers of FIG. 1 and FIG. 2, can beconfigured to perform one or more steps of the process 300 describedbelow. In some embodiments, the one or more devices performing the stepsare associated with a financial institution. In other embodiments, theone or more devices performing the steps are associated with a merchant,business, partner, third party, credit agency, account holder, and/oruser.

As illustrated at block 302, catalog data from one or more catalogsystems is retrieved. The catalog data includes item identifiers, itemdescriptions, categories, mapping configurations, system requirements,order fulfillment information, and the like. In some embodiments, a“crawl” API or other data retrieval tool is used to identify andretrieve catalog data as described herein above.

As illustrated at block 304, the catalog data is imported into a unifiedcatalog system or other system of process 300. The unified catalogsystem serves as a central hub for the one or more catalog systems andprovides the unified product catalog system to the user. The one or morecatalog systems are disparate and independent underlying systems thatfeed into the unified catalog system. The catalog data may be importedinto the unified catalog system in any way. For example, anadministrator of the unified catalog system may simply copy and pasteREST APIs (e.g., API's in the form of URLs) to import the catalog data.

As illustrated at block 306, changes are made to the catalog data. Insome embodiments, items descriptions, item names, item images, prices,identifiers, and the like are modified, deleted, added, reformatted, orotherwise edited. In some embodiments, an administrator associated withthe system is granted permission to make the modifications. For example,the system of process 300 may assign roles to individuals based on arole based administrative function. This role based assignment allowscertain individuals to edit certain types of data. Some editing tasks,for example, may require that some items such as new products use hardcode to make modification to the data. In such cases, only certainindividuals who have the capacity, authority, and/or expertise will begranted permission to implement changes for new products or other typesof data.

FIG. 5 illustrates a GUI 500 of an administrative catalog item tool 510that is accessible by an administrator for editing the catalog data andmaintaining individual catalog items. The GUI 500 includes various tabspositioned near the top of the screen for catalog crawling, HTML snippettools, index administration tasks, order status, order types, creatingitem packages, editing and reviewing source category mapping (see, e.g.,FIG. 7), source systems, synonyms configurations (see, FIG. 6), usermodes, and users. In the illustrated embodiment, the “Catalog Items” tabis selected.

The catalog item tool 510 presents a table that includes variousinformation related to a particular catalog item including item IDs(e.g., an internal numeric code used by the unified catalog system),item names, product category for each item, source systems, and thestock keeping unit (SKU) for each item. As shown in FIG. 5, theadministrator has selected the “2 Gigabytes Memory” item to edit. Ifmore than one source system supplies the selected item, theadministrator may select the source system used to fulfill the itemusing a drop down box 520 for source systems. In some embodiments, theadministrator may select more than one source system or create priorityrules for determining which system fulfills a particular item. Forexample, the system may implement priority rules to determine ratingassignments to rank the most preferred order fulfillment system. Thesystem with the most expertise and resources for printing services, forexample, may receive the highest priority and deemed the preferredsystem. The ratings may also be based on historical performance such aswhether a particular system met SLA deadlines in the past six months,user satisfaction surveys, order frequency, and the like. The priorityratings may be based on an item-by-item basis or based on anorder-by-order basis. For example, order may have include a single itemassociated with a single or multiple catalog systems or the order mayinclude multiple items associated with a single catalog system ormultiple catalog systems. In situations where the highest ranked or mostpreferred system cannot fulfill an order due to item backorders,backlogs, low resources, technical issues, and the like, the order datamay be sent to the second highest ranked in the second preferred system.In other cases, the system of process 30 may simply identify the systemthat has the ordered item in stock and that can fulfill the order withinthe SLA time frame. In other embodiments, the administrator may add,remove, or adjust new systems via a system table (not shown). Suchchanges may occur before the underlying source system is crawled toretrieve data. For example, if a new system is to be associated with theunified product catalog, an administrator may delete an old system orsimply add the new system as a source system before catalog data isretrieved for the newly added system.

Also provided by the catalog item tool 510 is a description box 522 thatallows the administrator to modify the description for the selecteditem. The administrator may edit the item description for a particularitem to update product information, make corrections, provide more orless details, and the like. The administrator can position a cursorwithin the description box to add and/or delete text. SLA box 524presents the current service level agreement terms that define how longit will take for the system to fulfill the order, which may be increasedor decreased by the administrator. In some cases, the SLA can beincreased or decreased automatically or manually based on input from theone or more catalog systems, the season, historical performance trends,the number of pending orders, catalog user traffic, and the like. Theadministrator may also include, remove, or modify permalinks and displaySKUs in permalinks box 526 and display SKUs box 528, respectively.

Further provided in GUI 500 is a disabled box 530 for indicating whetherthe selected item should be disabled in the unified catalog system, agroup box 532 for determining if the product should be limited to aparticular group for ordering (e.g., employees enrolled in the “MyWork”program), and one or more image boxes 534 for selecting or changing theimages displayed to the user in the unified product catalog. An item canbe disabled if the system determines that it has an “unorderable”status. For example, the item may be discontinued, unavailable,outdated, or incompatible with other items in the order. Further, theone or more catalog systems that fulfill the item may prefer that theitem be ordered directly and not through the unified product catalog.Labor intense products, complicated items, time or security sensitiveitems, and items that must be tracked may be better serviced andfulfilled directly from the one or more source catalogs.

Referring again to FIG. 5, a product category box 536 is shown thatallows the administrator to change, delete, or include additionalproduct categories that the selected item will be associated in. Theselected item may be included in one product category or multiplecategories. A name box 538 allows the administrator to modify the nameof the product (or not) by positioning the cursor in the name box 538and modifying the text therein. The administrator can input, delete, ormodify an API for the selected item in the API box 540. Further, theadministrator can also modify the listed price or source system SKU inthe price box 542 and the SKU box 544, respectively. The visible box546, the test item box 548, and the approval required box 550 allows theuser to change the status for each box (i.e., yes or no) if needed.

Referring now to FIG. 6, a GUI 600 of a synonyms maintenance table 610is illustrated and provides a way to associate multiple additional wordsor phrases with a particular catalog item. An administrator may accessthe synonyms maintenance table 610 by selecting the “Synonyms” tab shownin GUI 500 of FIG. 5. The maintenance table 610 includes a list of itemidentifiers, the associated name of the catalog item, and the synonymvalue for each item. In the illustrated embodiment, the administratorhas selected “Item 6” and has assigned a synonym of “Software 1.” Thetable 610 lists several different items that have been associated withthe synonym of Software 1 such that any search-hit on the synonym or anitem name assigned to that synonym will be treated as a positive hit forthose particular items. Other items such as Items 13-15 are associatedwith the same software synonym and the remaining times have also beenassociated with various other synonyms. The administrator can use thesynonym maintenance table 610 to modify the synonym associations withvarious items to create the optimal searching experience for the user inthe unified product catalog.

In further embodiments, the system of process 300 is configured tore-categorize items. FIG. 7 illustrates a GUI 700 featuring a sourcecategory mapping tool 710. The mapping tool 700 enables an administratorto map the categories in the underlying catalog systems to the highlevel product categories of the unified catalog system. In theillustrated embodiments, a variety of “Application Services” categoriesand sub-categories in an underlying catalog are being mapped to thehigh-level “Application Services” category of the unified catalogsystem.

In further embodiments, required fields for the fulfillment of ordersare configured and mapped. FIG. 8 illustrates a GUI 800 of a requiredfield tool 810, which allows an administrator to configure theinformation needs that are required to be obtained from a user for eachcatalog item to fulfill an order. The administrator can filter the listof required fields to a specific catalog item and search for fieldsmeeting certain criteria (e.g., all field containing the label“telephone”).

As shown in the illustrated embodiment, there are a number of detailsfor a new required field that can be set from the GUI 800 including thedisplay order, field data type, whether or not the particular field isrequired, customized drop-down values, and the like. A “progressivedisclosure” relationship can be set up where a specific answer to onequestion may cause additional questions to be displayed and so forth.The administrator can used the required field tool 810 to edit whichcatalog items use a particular required field, link the required fieldas a parent to dependent fields inputted or selected by theadministrator, or link the required field as a child dependent field tofields the administrator selects. Further, the administrator can selectparticular items from a list that will be included in the new requiredfield illustrated in FIG. 8.

As discussed in more detail below, the system of process 300 canconfigure the required fields such that the same question is never askedtwice. For example, if the user is asked for name and telephone numberfor one order or for one item in an order, the system will automaticallyuse that information for placing and fulfilling other items in the orderor other orders. Further, the system can also auto-populate fields basedon data extracted from a user's employee number, login information,saved template, previous order, stored data, and the like.

In other cases, the tool 810 has an option to treat a particular fieldas unique to override the process for avoiding repetition of questions.For example, the system may prompt the user to answer the same questionmultiple times. If a user is ordering 3 copies of a specific softwareproduct, it may be determined that the software products are beingordered on behalf of other users. In such cases, the user is asked toinput the intended recipient for each copy.

In further embodiments, the system of process 300 creates a productpackage. The system identified related items from the catalog data suchas products associated with a particular product category, items neededby a certain group of people (e.g., new employees), items associatedwith a brand or manufacturer, and the like. The related items can thenbe linked to generate a product package that can be presented to theuser via the unified product catalog.

Returning now to FIG. 3, a user interface for browsing and/or orderingitems from unified catalog system is provided to a user as illustratedat block 308. FIG. 9 illustrates a GUI 900 of a homepage 910 of theunified product catalog. The user may be required to log into thecatalog by inputting a user name, employee ID, password, biometric data,or other security information to log into the unified product catalog.The homepage 910 includes a search tool for finding specific items usingkeyword or product ID. Additionally, the homepage 910 includes certainproduct categories for the user to browse. The product categoriesinclude access management, accessories, business services,collaboration, and so forth. To track orders, view or save templates,contact customer service, track previous order, change ordering orpersonal information, the user can select the requisite tabs near thetop of the homepage 910.

As illustrated at block 310 of FIG. 3, a request for a selected item isreceived from the user. For example, the user may select a product fromthe categories or from a list generated by a keyword search in theunified product catalog. If the item is determined to be orderable, itis placed in the user's shopping cart.

As illustrated at block 312, an identifier of the item is identified.The item identifier comprises code, text, number, and/or symbols thatenable the system of process 300 to identify and fulfill an order. Insome embodiments, the identifier or product code displayed to the useris the same or different than the item identifier. For example, theproduct code displayed on the online product catalog may be an internalidentifier used by the unified catalog system to keep track of items,and/or an SKU. The internal identifier or SKU may be different from theSKU in the unified catalog system. The item identifier, for example, maybe the SKU or other code associated with the one or more catalog systemsproviding the item, and different from the displayed product code, orthe displayed product code and the item identifier may be the same. Insome cases, an internal code may be displayed if there is more than oneSKU or catalog system associated with the selected item. The internalcode can be used to identify all items associated with that internalcode.

As illustrated at block 314, the item is matched to a source catalogbased on the identifier. The one or more catalog systems manage, own, orare otherwise associated with the source catalog. The source catalog isthe catalog that provides, maintains, and/or fulfills the matched itemor orders for the matched item.

In further embodiments, duplicate items are identified based on the itemidentifier. SKUs, for example, can be used to identify multiple itemsthat are supplied and serviced by multiple catalog systems. In suchcases, at least a portion of the duplicate are removed such that onlyitem is displayed to the user and not several copies of the exact sameitem. Some or all of the duplicates can also be removed or suppressedbased on priority rules that govern which catalog systems is thepreferred systems for supplying the items. The items associated with thepreferred catalog systems may be retained and all other duplicate itemscan be removed. In other cases, the duplicate items associated with thenon-preferred catalog systems may be retained in storage so that thesystem can identify the systems that supply the particular item shouldthe preferred system be incapable of fulfilling an order.

Referring now to FIG. 4, the process 300 is further illustrated. Asillustrated at decision block 402, the system of process 300 determinesif there are order restrictions for the selected item. The orderrestrictions include rules that determine whether an item is orderable.The rules can be based on delay times, item quantity maximums, SLAperiods, stock quantity, the identity of the fulfilling catalog system,and so forth. Some items may be deemed orderable or unorderable based onany number of factors including item popularity, frequency an item isordered, reported glitches or issues with an item, fluctuations inproduction, item discontinuations, items costs, amount of support neededfor an item, user reviews, and the like. In some cases, unorderableitems will not appear on the unified product catalog or the user may notbe able to select the item for ordering (e.g., the item may be greyedout). In other cases, the orderability status of the item may changesuch that the user may be able to view and select an item, but may notbe able to order the item from the unified product catalog.

As illustrated at block 404, a notification is provided to the user iforder restrictions are detected. In cases where the item cannot beordered due to the orderability status associated with the selecteditem, the notification can include the orderability status, reasons forthe orderability status, suggestions for similar items, and the like.For example, if there is a backlog, logistical issues, or stockingissues associated with the selected item, the notification may includethe expected amount of delay to fulfill the item, the reason for thedelay, alternative items, and/or alternative channels for ordering theselected item. In still other embodiments, the notification includes alink for the underlying catalog system associated with the selecteditem. For example, some items may only be ordered directly from thesource catalog and cannot be ordered from the unified product catalog.

As illustrated at block 406, required fields for order fulfillment areidentified and provided to the user. FIG. 10 illustrates a GUI 1000 ofan order 1010. In the illustrated embodiment, the user has selected fouritems that appear in the user's shopping cart. The order 1010 includes apicture of each item, the name and quantity of each item, the designatedsource catalog system for each item, the SLA number, and the cost. Thesystem of process 300 allows the user to change the quantity of eachitem. Even in cases where the underlying system that has been designatedto fulfill the item does not allow more than 1 item to be ordered at atime, the unified product catalog can allow the user to order more thanthe underlying catalog system's maximum quantity. This is because thesystem of process 300 may can simply use an order API to call theunderlying system any number of times in order to fulfill the quantityrequested by the user. Further, the system can also set minimum ormaximum quantities for items independent of the underlying systems. Forexample, the system may require that 3 ink cartridges be ordered at atime in order to save on shipping costs regardless of the minimumquantities set for ink cartridges by the one or more catalog systems.

Returning now to FIG. 10, on the side portion of the GUI 1000, orderinformation detailing required data needed at checkout is provided. Thisportion of the GUI 1000 allows the user to change order recipients orconduct a test checkout. The test checkout allows the user to screenwhat information will be required of them during checkout. The GUI 1000also illustrates a “Save as Template” option which allows the user tosave the order as a template to use for future orders with or withoutcompleting the checkout process. The saved template can be used toautomatically populate the user's cart in the future before the usercheckouts. The user may also add new items and checkout using the savetemplate, or the user can add new items and save the new cart (savedtemplate+new items) as a new template. If a user chooses to add an ordertemplate to the cart when there are existing items in the cart, the userwill be prompted to clear the cart first or to merge the template withthe cart. If they chose the merge option, any duplicate items can beautomatically removed so that overlapping items are not double-added. Inother cases, the system determines that duplicates exist in the shoppingcart, and then prompts the user to answer whether or not the userintended to increase the quantity of the duplicate item. If the useronly intended to order one mouse, for example, the user may decrease thequantity of mice to one. The required fields, in some embodiments, areprovided to the user during checkout as discussed in more detail belowwith regard to FIG. 11.

Returning now to FIG. 4, required fields are auto-populated and/or inputfrom the user is requested as illustrated at block 408. In someembodiments, the required fields are auto-populated based on internaldefault information databases. For example, the system of process 300may have access to a wide variety of information for each user and maynot require the user to input information (e.g., computer identifiers,phone, address, cost center, and so forth) contained in other databasesthat accessible to the system. FIG. 11 provides a GUI 1100 that includesthe required fields in an order details page 1110. The user can accessthe order details page 1110 by selecting the “Proceed to checkout”button on the GUI 1000 of FIG. 10. Because the cart from the order 1010includes two software products, the exact same required fields areneeded to complete the order for these items. This common information isauto-populated at the top of the GUI 1100. For example, phone number,cost center, and company code fields are auto-populated based on theuser's login information, employee number, previous orders, and thelike. This prevents the user from having to answer the same questiontwice. Some required fields in the common information top portion maynot be auto-populated (e.g., password and region) and require userinput.

Further provided in the order details page 1110 is a unique productinformation portion positioned beneath the common order informationportion. For this particular order displayed in FIG. 11, the web cam andmonitor each have additional required fields that require the user toanswer questions or input additional information. Once the user hascompleted entering information in the required fields, the user canselect the button at the bottom of the GUI 1100 to place the order.

Returning now to FIG. 4, order data comprising the user input and itemdata is sent to the source catalog for order fulfillment and processingas illustrated at block 410. A single order may have multiple items fromthe same or different sources. In some embodiments, a single item isassociated with multiple source catalogs. For example, a softwareprogram may be in three underlying source catalogs. In such cases, thesystem of process 300 follows priority fulfillment rules as discussedabove. The source catalog receives the order data and fulfills the orderwithin the SLA and other order parameters. The user may track theprogress of the order fulfillment via the unified product catalog.

In some embodiments, a refusal of at least a portion of the order isreceived from the source catalog. For example, the source catalog mayhave a backlog of orders and may not be able to meet the order SLA. Inother examples, the source catalog may not have the selected item instock. In such cases, the system of process 300 follows order parametersand rules. The order parameters can include a fulfillment priority suchthat a second source catalog fulfills the order when the first sourcecatalog cannot. In other cases, the order may be fulfilled using a thirdparty source (e.g., an outside vendor) if the items relate to security,are time sensitive, are critical to the user's work production, and thelike. In still other cases, the system provides the user with anotification if there will be a delay in the fulfillment of the order,or if a portion of the order cannot be fulfilled.

FIG. 12 is a GUI 1200 of product detail page 1210. In some embodiments,the product detail page 1210 may be provided to the user while browsingand placing an order, or before placing an order. In the illustratedembodiment, a mobile device description page of a particular mobiledevice in a mobile device category is provided to the user. Near the topof the page, an image of the mobile device 1, the price, and a briefproduct description are provided. Below the top portion are a morecomplete description of the mobile device 1 and a section listing andproviding links to articles associated with mobile device 1 or mobiledevices in general. In some embodiments, the articles or otheradditional data is retrieved from external systems. In particularembodiments, the articles are identified by passing the item name intoan internal knowledge based search engine. In the illustratedembodiments, the first 10 hits from the engine search are displayed.Further included in the product detail page 1210 is a frequently ordertogether section, which displays items that have been included in pastorder associated with the mobile device 1.

In some embodiments, administrators have permission to select an editbutton (not shown) on the product detail page 1210. In this way, productdescription can be dynamically edited on the product detail page 1210instead of using a dedicated maintenance screen.

Further illustrated in FIG. 12, is a “Frequently Order Together” sectionnear the bottom of the GUI 1200. Frequently ordered items or popularitems are calculated by the system based on the information supplied bythe unified product catalog. This is advantageous because the frequentitems are determined based on all of the ordering data from the one ormore catalogs and not just one underlying catalog system.

The flowcharts and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods and computer program products according to variousembodiments of the present disclosure. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof code, which comprises one or more executable instructions forimplementing the specified logical function(s). It should also be notedthat, in some alternative implementations, the functions noted in theblock may occur out of the order noted in the figures. For example, twoblocks shown in succession may, in fact, be executed substantiallyconcurrently, or the blocks may sometimes be executed in the reverseorder, depending upon the functionality involved. It will also be notedthat each block of the block diagrams and/or flowchart illustration, andcombinations of blocks in the block diagrams and/or flowchartillustration, can be implemented by special purpose hardware-basedsystems which perform the specified functions or acts, or combinationsof special purpose hardware and computer instructions.

The terminology used herein is for the purpose of describing particularembodiments only and is not intended to be limiting of embodiments ofthe disclosure. As used herein, the singular forms “a,” “an,” and “the”are intended to include the plural forms as well, unless the contextclearly indicates otherwise. It will be further understood that theterms “comprises” and/or “comprising,” when used in this specification,specify the presence of stated features, integers, steps, operations,elements, and/or components, but do not preclude the presence oraddition of one or more other features, integers, steps, operations,elements, components, and/or teams thereof.

The corresponding structures, materials, acts, and equivalents of allmeans or step plus function elements in the claims below are intended toinclude any structure, material, or act for performing the function incombination with other claimed elements as specifically claimed. Thedescription of the present disclosure has been presented for purposes ofillustration and description, but is not intended to be exhaustive orlimited to embodiments of the disclosure in the form disclosed. Manymodifications and variations will be apparent to those of ordinary skillin the art without departing from the scope and spirit of embodiments ofthe disclosure. The embodiment was chosen and described in order to bestexplain the principles of embodiments of the disclosure and thepractical application, and to enable others of ordinary skill in the artto understand embodiments of the disclosure for various embodiments withvarious modifications as are suited to the particular use contemplated.Although specific embodiments have been illustrated and describedherein, those of ordinary skill in the art appreciate that anyarrangement which is calculated to achieve the same purpose may besubstituted for the specific embodiments shown and that embodiments ofthe disclosure have other applications in other environments. Thisapplication is intended to cover any adaptations or variations of thepresent disclosure. The following claims are in no way intended to limitthe scope of embodiments of the disclosure to the specific embodimentsdescribed herein.

What is claimed is:
 1. A system for providing a unified catalog, wherebythe system collects, manages, and edits catalog data from disparatecatalog systems, the system comprising: a computer apparatus including aprocessor and a memory; and a software module stored in the memory,comprising executable instructions that when executed by the processorcause the processor to: import catalog data from one or more underlyingcatalog systems; identify items from the catalog data; modify at leastone of item descriptions, item names, product categories, and itemidentifiers associated with the identified items; provide a unified userinterface to a user for browsing the items; receive a request for atleast one product selected by the user from the items; and send an orderfor the at least one selected product to the one or more catalogsystems.
 2. The system of claim 1, wherein the executable instructionsfurther cause the processor to: identify a first product categorycomprising at least one category item; transfer the at least onecategory item to a second product category.
 3. The system of claim 2,wherein the at least one category item appears in the first productcategory and the second product category
 4. The system of claim 2,wherein the executable instructions further cause the processor to:collapse the first product category.
 5. The system of claim 2, whereinthe executable instructions further cause the processor to: rename thefirst product category.
 6. The system of claim 1, wherein the executableinstructions further cause the processor to: identify related itemsassociated with a product category from the catalog data; create aproduct package comprising the related items; present the productpackage to the user via the user interface.
 7. The system of claim 1,wherein the executable instructions further cause the processor to: setat least one of a service level agreement (SLA) time period, a usergroup, and approval requirements for the items.
 8. The system of claim1, wherein the executable instructions further cause the processor to:determine a unique identifier associated with each of the items;identify duplicates of a single item from multiple catalog systems basedon the unique identifier; identify a preferred catalog system; retainthe single item associated with the preferred catalog system and removeall other duplicates.
 9. The system of claim 1, wherein the executableinstructions further cause the processor to: dynamically edit displayeddata in the user interface.
 10. The system of claim 1, wherein theexecutable instructions further cause the processor to: identify aplurality of related items having a plurality of different names; assigna synonym to each of the related items; allow the user to conduct anitem search using one of the different names; display all of the relateditems in response to the search and based on the synonym assignment. 11.The system of claim 1, wherein the user is unaware that the order isfulfilled by the one or more catalog systems.
 12. A computer programproduct for providing a unified catalog, whereby the computer programproduct collects, manages, and edits catalog data from disparate catalogsystems, the computer program product comprising: a non-transitorycomputer readable storage medium having computer readable program codeembodied therewith, the computer readable program code comprising:computer readable program code configured to import catalog data fromone or more underlying catalog systems; computer readable program codeconfigured to identify items from the catalog data; computer readableprogram code configured to modify at least one of item descriptions,item names, product categories, and item identifiers associated with theidentified items; computer readable program code configured to provide aunified user interface to a user for browsing the items; computerreadable program code configured to receive a request for at least oneproduct selected by the user from the items; and computer readableprogram code configured to send an order for the at least one selectedproduct to the one or more catalog systems.
 13. The computer programproduct of claim 12, further comprising computer readable program codeconfigured to identify a first product category comprising at least onecategory item and transfer the at least one category item to a secondproduct category.
 14. The computer program product of claim 13, whereinthe at least one category item appears in the first product category andthe second product category
 15. The computer program product of claim12, further comprising computer readable program code configured todetermine a unique identifier associated with each of the items;identify duplicates of a single item from multiple catalog systems basedon the unique identifier; identify a preferred catalog system; andretain the single item associated with the preferred catalog system andremove all other duplicates.
 16. The computer program product of claim12, further comprising computer readable program code configured toidentify a plurality of related items having a plurality of differentnames; assign a synonym to each of the related items; allow the user toconduct an item search using one of the different names; and display allof the related items in response to the search and based on the synonymassignment.
 17. A computer-implemented method for providing a unifiedcatalog, the method comprising: importing, by a processor. catalog datafrom one or more underlying catalog systems; identifying, by aprocessor, items from the catalog data; modifying, by a processor, atleast one of item descriptions, item names, product categories, and itemidentifiers associated with the identified items; providing, by aprocessor, a unified user interface to a user for browsing the items;receiving a request for at least one product selected by the user fromthe items; and sending, by a processor, an order for the at least oneselected product to the one or more catalog systems.
 18. Thecomputer-implemented method of claim 17, further comprising:identifying, by a processor, a first product category comprising atleast one category item; transferring, by a processor, the at least onecategory item to a second product category.
 19. The computer-implementedmethod of claim 17, further comprising: determining, by a processor, aunique identifier associated with each of the items; identifying, by aprocessor, duplicates of a single item from multiple catalog systemsbased on the unique identifier; identifying a preferred catalog system;retaining the single item associated with the preferred catalog systemand remove all other duplicates.
 20. The computer-implemented method ofclaim 17, further comprising: identifying a plurality of related itemshaving a plurality of different names; assigning a synonym to each ofthe related items; allowing the user to conduct an item search using oneof the different names; displaying all of the related items in responseto the search and based on the synonym assignment.